Automatic Replanning of Task Networks for Process Model Evolution in EPOS

Evolutionis crucial inSoftwareProcess Modeling(PM) and tems. EPOSis aPMsupport system, usingthe sameConss Schema (types PM0. Pr ovi de PMSuppor t : pr oces s mode l i ng l anguage , pr oces s t ool s . PM1. El i c i t r equi r ement s f or pr oces s mode l . PM2. Anal ys e/des i gn a templ ate model ( \s ymbol i c pr ogr am") . PM3. Impl ement an enactabl e model ( \l oad i mage") . PM4. Execut i ng an enacting model ( \r unni ng i mage") . PM5. As s es s ext er nal pr oces s per f ormance . Ther e i s no as s umpt i on t hat t he phas es PM1{PM5 s houl d \wat er f al l " s equence f or al l par t s of t he mode l . l at e / dynami c bi ndi ng, t he di s t i nct i ( i ns t ant i at ed) and enact i of pr oces s mo t o expr es s and r eas on about decompos ed and de l ayed/l ongt ermact i vi t i e s ; s ee [ CLJ91] f or a di s cus s i on. I n MELMAC, pr oces s mode l s ar e expr es s ed as r e nabl e FUNSOFT net s . Some t r ans i t i on nodes can r epr es ent modi cation points, t o be be manual l y expanded be f or e execut i ng i t . The networ k can onl y evol ve ver t i cal l y t al l y, and r edoi ng a networ k dynami cal l y i s pr obabl y n SPADE, empl oyi ng an ext ended Pet r i net duced r e ect i on t o manage pr oces s e dynami cal l y and i ncr eme bas ed on exi s ge 3 AnOverview of EPOS EPOS [ COWL91] i s a mul t i us er , ker ne l s of twar e engi neer i ng envi r onment , cover i ng bot h Con gur at i on Management (CM) , PMand Pr oces s Management . I n t he next s ubs ect i ons we wi l l pr es ent t he EPOSDB, t he SPELL l anguage , s ome exampl es us i ng SPELL, and t he t hr ee bas i c EPOS PMt ool s : Schema ager , Execut i on Manager , and Pl anner . The emphas i s i s on t he Pl t he demands f or r epl anni ng. APr oj ect Manager and a Coo s ket ched i n Sect i on 4 on t he EPOS met apr oces s . 3. 1 The EPOSDB Al l pr oces s ar t i f act s ar e r epr es ent ed by r e l at i ons hi ps . Aprocess mode and r e l at i ons hi ps , The e Tas ks ar e connect ed i n a typed task network wi t h chai ni ng and decompos i t i on. The "hor i zont al " par t of t he networ k r es embl es a Pet r i net , wher e t r ans i t i on nodes ( t as ks ) ar e connect ed wi t h pl aces ( pr oduct s i n EPOS) . The typel eve l at t r i but es s e r ve as s har ed process parameters, and r ede ned by s ubtypi ng and ver s i oned between pr oj ect s . Mos pr ocedur es and at t r i but es ar e us ed t o i ns t r umen s ome of t he i ns t ance l eve l pr ocedur e AProcess Schema i s a s et of t he TaskEntity t ype and i t DataEntity an i s t he